<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**
This is a follow-up to address feedback from
#23060.

### Changes
- Bumped @metamask/transaction-controller to version ^62.2.0
- Replaced `MUSD_CONVERSION_TRANSACTION_TYPE` with
`TransactionType.musdConversion` from transaction-controller
- Added `skipInitialGasEstimate: true` when creating mUSD conversion
transaction to improve performance. Gas estimate is now calculate
asynchronously
- Fixed case where user could be redirected to previous page prematurely
when calling `initiateConversion` from `useMusdConversion` hook.
- Removed transition header from mUSD conversion confirmation screen. We
no longer see the default blue back arrow and screen title while
navigating to the confirmation screen.
<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: follow up musd conversion optimizations based on #23060
feedback
## **Related issues**

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Switch to TransactionType.musdConversion with async gas estimation, UX
tweaks, and controller bump to ^62.2.0.
> 
> - **mUSD conversion flow (Earn)**:
> - Use `TransactionType.musdConversion` across hooks, components, and
tests (replacing custom `MUSD_CONVERSION_TRANSACTION_TYPE`).
> - Create transactions with `skipInitialGasEstimate: true` for faster
first paint; add nested transactions; improve error handling to avoid
stuck screens.
> - Hide header on `REDESIGNED_CONFIRMATIONS` route for a cleaner
transition.
> - Update confirmation UI to recognize new type: `info-root`, `footer`,
`custom-amount-info`, `bridge-fee-row`, and `musd-conversion-info`
label/tooltip logic.
> - **Controller/engine**:
> - Bump `@metamask/transaction-controller` to `^62.2.0` and update Yarn
lock; minor init adjustments (registry access, typings).
> - **Tests**:
> - Update unit tests to reflect new transaction type and async gas
estimation behavior.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
865d6a4. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## **Description**

Prevent no quotes alert message being displayed inside button.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes: #23098 

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Adds a `title` to the `NoPayTokenQuotes` alert and updates tests and
English locale strings accordingly.
> 
> - **Alerts**
> - Add `title: strings('alert_system.no_pay_token_quotes.title')` to
`useNoPayTokenQuotesAlert` in
`app/components/Views/confirmations/hooks/alerts/useNoPayTokenQuotesAlert.ts`.
> - **Tests**
> - Update expectations in `useNoPayTokenQuotesAlert.test.ts` to include
`title`.
> - **i18n**
> - Add `alert_system.no_pay_token_quotes.title` ("No quotes") in
`locales/languages/en.json` and keep existing `message`.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
0650421. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## **Description**

Ensure keyboard is shown on top of modal.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes: #23139 

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

<img width="300" alt="Keyboard"
src="https://github.com/user-attachments/assets/f90e8f63-1f19-4cde-b278-1e84ed11b29d"
/>

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Sets `keyboardAvoidingViewEnabled={false}` on `BottomSheet` in
`PayWithModal` to change keyboard behavior.
> 
> - **UI**:
> -
`app/components/Views/confirmations/components/modals/pay-with-modal/pay-with-modal.tsx`
> - Pass `keyboardAvoidingViewEnabled={false}` to `BottomSheet` in
`PayWithModal`.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
52f6beb. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

## **Description**

When displaying network permissions in the
`MultichainPermissionsSummary` component, network avatars without an
`imageSource` property were being passed to the `AvatarGroup` component,
which could result in `undefined` values in the avatars array. This
caused potential rendering issues and inconsistent UI behavior when
displaying network permissions.


<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: Fixed network avatar display issue in permissions when
network images are unavailable

## **Related issues**

Fixes:

## **Manual testing steps**

```gherkin
Feature: my feature name

  Scenario: user [verb for user action]
    Given [describe expected initial app state]

    When user [verb for user action]
    Then [describe expected outcome]
```

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

<!-- [screenshots/recordings] -->



https://github.com/user-attachments/assets/860f2212-4930-4f5f-91c9-245d37c31841



### **After**

<!-- [screenshots/recordings] -->


<img width="453" height="908" alt="Screenshot 2025-10-30 at 11 51 44"
src="https://github.com/user-attachments/assets/c8753158-6df7-4a21-ba1e-cc7dad52fae4"
/>

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Filters out non-CAIP wallet scopes when generating network avatars and
adds tests to validate image source calls and chain ID formats.
> 
> - **Permissions UI**:
> - In `MultichainAccountPermissions.tsx`, validate and filter
`selectedChainIds` to include only valid CAIP chain IDs and exclude
`wallet:` scopes before creating `networkAvatars` (uses
`isCaipChainId`).
> - **Tests**:
> - Update `MultichainAccountPermissions.test.tsx` to mock
`getNetworkImageSource` and add a `networkAvatars` test ensuring no
`wallet:` scopes are passed and only valid CAIP chain IDs are used.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
fce0c16. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## **Description**

Prevent infinite loader when updating amount with same value in metamask
pay.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes: #23132 #22785 

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Avoids unnecessary updates by early-returning when the new token
amount equals the current amount, with tests added.
> 
> - **Hooks**:
> - Update `useUpdateTokenAmount` to early-return if `newAmountRaw`
equals current `amountRaw`, preventing transaction data updates in
`useUpdateTokenAmount.ts`.
> - **Tests**:
> - Add test in `useUpdateTokenAmount.test.ts` asserting no calls to
`updateEditableParams` or `updateAtomicBatchData` when amount is
unchanged.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
be98771. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## **Description**

Automatically select the highest balance token on any chain in Perps and
Predict deposits.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes: #23131 

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Simplifies automatic pay token selection to the first available token
with balance, falling back to target token when none or on hardware
wallets, and updates tests accordingly.
> 
> - **Logic (useAutomaticTransactionPayToken.ts)**
> - Replace multi-step selection (target match → highest balance same
chain → highest balance alt chain) with simple rule: pick `tokens[0]` if
any; otherwise fall back to required target token; always fall back for
hardware wallets.
> - **Tests (useAutomaticTransactionPayToken.test.ts)**
>   - Update expectations to select the first available token.
>   - Remove scenarios around highest-balance and cross-chain selection.
> - Keep fallbacks: target token when no tokens, hardware wallets, and
disabled state does nothing.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
6907490. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## **Description**

Update text colour of Predict claim button in light theme.

## **Changelog**

CHANGELOG entry: null

## **Related issues**

Fixes: #23096 

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

<img width="300" alt="Claim"
src="https://github.com/user-attachments/assets/cf4f7ecc-ba59-48c7-a6a9-88cff992c7c4"
/>

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [x] I've completed the PR template to the best of my ability
- [x] I’ve included tests if applicable
- [x] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [x] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Replace Predict claim CTA with ButtonHero and drop
light-theme-specific button styling.
> 
> - **Predict Claim Footer (`predict-claim-footer.tsx`)**:
> - Replace `Button` with `ButtonHero`; move label to children, remove
variant/label props.
>   - Set `size` to `ButtonBaseSize.Lg` and `isFullWidth`.
>   - Add imports for `ButtonHero` and `ButtonBaseSize`.
> - **Styles (`predict-claim-footer.styles.ts`)**:
> - Remove hardcoded `button` style and `lightTheme` dependency; keep
container/top/bottom styles.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
44a2213. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->